

Helped Me on my Way
Provacative and challengingOn page 163 he notes: "A great portion of creation within the Creator's purposive will; there is also a portion of creation outside his purposive will, but this is there in accordance with his permissive will. " That "According to Christian belief, the connection between the human creature and his Creator is unique. All nonhuman creatures prefectly obey tye Creator's will because they have no self-determination."
"In contrast to Zen, for which all thoughts and all individual minds are the Only-Mind, the Bible depicts the ultimate thoughts of the Creator to be far beyond the capacity of created human minds to comprehend : My thoughts are not your thoughts, Neither are your ways my ways, says the Lord. For as the heavens are higher than your ways, And my thoughts higher than your thoughts (Isaiah 55:8)" In such passages, genuine separation between the mind of the Creator and the minds of human creatures is clearly affirmed."
"Let me assure my Buddhist readers that to be a Christian does not require one to believe in a God who is like an old man with a white beard who flies through the sky on feathered wings." I think Christians need to be reminded of this as well.
On page 167 he reminds the reader that " The tranquility which Zen gives rests upon the realization that there is nonresponsibility to pursue what is "good" and to flee what is "evil". The essence of Zen peace is the glad acceptance of everthing just as it is." "For Zen, there is no sin. For Jesus, all have sinned." This is disagree with, since this is pure Paulist thought and a thought that has wreaked havok on humanity.
The author then notes wisely, I might add that most of the assertaions he makes are equally shared with his Jewish friends whos eunderstanding of the character of God the Creator comes from the Torah but NOT the Christian New Testament.He suggests that Jesus is very Budhhist in nature.
My first introduction to Zen

Good on examples of the functional approach to algorithmsI've read "Structure and Interpretation of Computer Programs" (SICP), and like many others found it one among the best if not *the best* computerbook I've ever read. I think that "The Functional Approach to Programming" differs a lot from SICP. This is not to say, that it's bad, rather that I think it's very different from SICP. Its focus is much more on semantics (ML of course, not Scheme), correctness (in the scientific sense) and algorithms.
It offers plenty on the functional approach to implementing algorithms like trees and sets. The semantics are elaborated in a clear and concise style, that I've been able to track even though I have no degree in computer science at all (I'm just an auto didact from "the street").
For someone not familiar with functional programming like me, I find this very good. I have a background in C, Java, C++ moving toward more highlevel languages like Scheme, Lisp, Ruby, SmallTalk and Python in the latter years.
It is very succinct with plenty of code examples like SICP. The code doesn't fill too much, since the functional style is a lot shorter for solving complex problems than the equavalent imperative program examples I've seen in C++ and Java. The focus is on the scientific correct thing to do, rather than a more ad hoc focus on "best practices" giving way to a more firm ground for choosing style and algorithms to solve a particular problem. The "best practices" are there of course, but in a transparent way, like small paradigms of code (somewhat like Peter Norvig's "Paradigms of Artificial Intelligence Programming - Case Studies in Common Lisp").
Just to make it clear: I don't think it's fair to compare it with SICP, although their subjects overlap somewhat. Its vocabulary differs significantly from both SICP and the terminology used in OO and Design Patterns land. This is bad in the sense in makes it unnecessary hard to learn the basics.
However, if you haven't dealt with functional programming before, you're of course going to encounter the usual paradigm shifting problems. I now find my self thinking a whole new and rather refreshing way about programs. It does pay off, even though it certainly helped that I had read SICP and a lot of articles on the subject at first.
Even if I'm never going to use functional programming in my professional life, I've now got a better grasp of algorithms -- what, when and how to use them. It's simply easier to reason about them using the functional approach.
By the way: The english translation *is* perfect.
Should you read it? I think you should, but prepare yourself to use some time to understand new concepts if you're not familiar with the nomenclature of the functional programming community. Even though it's not easy, I still think it pays off.
Great Book on Functional ProgrammingThe language of choice (CAML) used in this book requires some effort to learn. Certain elements of its syntax are non-obvious, and the internal type checking can be irritating until you learn that the rigorous checks result in safer programs. (An interesting side-note is that OCaml, compiled to native code, is in most cases very nearly identical in speed to straight C. Visit http://caml.inria.fr for details).
This is not an easy book. I found myself flipping to prior chapters to reread sections that I thought I understood on the first pass, but had not. This is no fault of the author, but rather the of the unfamiliar nature of the territory covered.
This book covers a lot of ground. As the other reviewer indicates, if you liked SICP, you will like this book. It covers a lot of the same ground, and provides an excellent grounding in various data structures and so forth.
One final note. Although the book is a translation from French, I found the english to be perfect. There were no slips into incorrect syntax or confusing idioms. My hat's off to the editor/translator.
A wonderful introduction to (functional) programming

Captured memories
great nostalgia for small-town American life

golf rules demystifiedInstead what we get are simple, straightforward explanations of the rules, and to make things even easier, illustrations (featuring Scottie IV, the rules terrier, drawn by Greg Clarke) are provided. I especially liked the way the book is arranged. Situations golfers are most likely to end up in are the first to be given priority. So right off the tee you'll have discussions on four areas: Out of bounds, lost balls, water hazards, and lateral water hazards. If you find yourself in a water hazard, these are the options available to the golfer according to the book:
A caveat to the reader: this is a book presented by the Callaway Golf Company, embroiled bitterly with the USGA, because of...well, the rules. The USGA wants the rules to be followed no matter what, whether you are Tiger Woods playing at Augusta or a weekend hacker playing at a rinky-dink golf course in the middle of nowhere. On the other hand, Callaway seems to support the notion that the rules can be a little flexible when golf is played for fun. In fact there is a section in the book where it actually says it's okay to ignore the rules in certain situations. Now this can get you into a lot of trouble, depending how serious your playing partners are about their golf game.
Aside from that, I think any golfer will find this book insightful and find it a handy reference on the golf course.


I recommend this book for every Christian guy!

Not a book for the dinofans
An excellent collection of papers on extinct marine reptiles

Synopsis
Better than that!
Couldn't put it down!!!For me its all about being entertained and being able to loose myself for a few hours... If that is what you are looking for then this book (in fact the ENTIRE series) is for you... ENJOY!!!!


This a basic book on the subject. To much expensive
